Metadata editing control

ABSTRACT

A metadata management architecture. The architecture includes a property component that lists one or more properties related to a file, and a viewing component that present files having one or more of the related properties. A synchronization component provides immediate synchronization between property editing fields of the property component and a view in the property-based browser component, providing both instantaneous feedback on property changes and an ability to manipulate properties graphically. Thus, a change in the property pane is immediately reflected in the view component, and a change in the view component is immediately reflected in the property pane.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.10/950,075, filed on Sep. 24, 2004, entitled “METADATA EDITING CONTROL”,which claims the benefit of U.S. Provisional Patent Application Ser. No.60/566,502, filed on Apr. 29, 2004, entitled “METADATA EDITING CONTROL”.The entireties of the aforementioned applications are incorporatedherein by reference.

TECHNICAL FIELD

This invention is related to data systems, and more specifically, tometadata editing and viewing mechanisms.

BACKGROUND OF THE INVENTION

Advances in information technology continue to demand increasinglylarger storage capabilities and consequently, improvements in the way auser can query and navigate through such large amounts of data.Computers and portable computing devices are ubiquitous with each classof devices having its own data access and management considerations. Insupport thereof, data storage techniques and access methodologiescontinue to evolve to meet these demands. However, such evolving systemscan take significant departures from conventional data access,navigation, and storage regimes. Thus, users who might have beenrelatively familiar with the traditional systems now must become savvyto the newer methodologies.

Currently, typical applications have a few menu commands that facilitatethe modification of document metadata (e.g., in a Microsoft OFFICE brandsuite of applications running on a WINDOWS XP brand operating system). ASave command is used to update the current version of the document onthe hard drive. For a new document being saved for the very first time,Save invokes a SaveAs dialog. Otherwise, the update is performedtransparently with no dialog. The SaveAs command creates a new versionof the document file on the hard drive, and starts by bringing up adialog window to set the properties needed to uniquely identify thefile.

In the Windows XP brand operating system, the identifying properties caninclude, for example, a file name, a file type (file name extension),and a location of the file in the folder tree (collectively, theseproperties are called a file path). The SaveAs dialog includes a foldertree browser similar to an Open dialog and a WINDOWS EXPLORER brandbrowser viewer. This reinforces the feeling of a folder as a place-ifthe file is placed there, it can be found there later. Additionally, thebrowser shows the other files in each folder location. This facilitatesan informed decision if a given folder is the right place to save thenew document. It also supports one-click copying of the file identifyingproperties—when an existing file is clicked, the new file name is set tothe same value and the newly-saved document assumes the identity andreplace the existing one.

A Properties option brings up a dialog to set the document metadata,such as Author, Title, Subject, Category, Keywords, Comments, etc. In aWindows XP brand operating system, document metadata are auxiliary—theycan be visible in the browser view, but they cannot actually be used tobrowse the disk content across multiple folders.

A Versions option allows the creation of multiple versions of thedocument. In a Windows XP brand operating system, versioning is notsupported at the system level; therefore, the implementation isapplication dependent. Many applications choose to keep all the versionsin a single file. Other applications allow setting the version property,but different versions must have different file identity and are notlinked together. Thus, user interaction with properties is cumbersomeand unfriendly.

What is needed is an improved metadata management system.

SUMMARY OF THE INVENTION

The following presents a simplified summary of the invention in order toprovide a basic understanding of some aspects of the invention. Thissummary is not an extensive overview of the invention. It is notintended to identify key/critical elements of the invention or todelineate the scope of the invention. Its sole purpose is to presentsome concepts of the invention in a simplified form as a prelude to themore detailed description that is presented later.

The invention disclosed and claimed herein, in one aspect thereof,comprises architecture for property editing control. The inventionprovides immediate synchronization between property editing fields of aproperty pane and a view in a property-based browser, providing bothinstantaneous feedback on property changes and an ability to manipulateproperties graphically. Thus, a change in the property pane isimmediately reflected in the view component, and a change in the viewcomponent is immediately reflected in the property pane.

In another aspect thereof, when browsing properties in the view,displaying a clustered view based on a mutable property automaticallyactivates visually a corresponding property editing field. However, ifdisplaying a clustered view based on an immutable property, editing ofthe corresponding property field is disabled.

In still another aspect of the subject invention, an artificialintelligence component is provided that employs a probabilistic and/orstatistical-based analysis to prognose or infer an action that a userdesires to be automatically performed.

To the accomplishment of the foregoing and related ends, certainillustrative aspects of the invention are described herein in connectionwith the following description and the annexed drawings. These aspectsare indicative, however, of but a few of the various ways in which theprinciples of the invention can be employed and the invention isintended to include all such aspects and their equivalents. Otheradvantages and novel features of the invention will become apparent fromthe following detailed description of the invention when considered inconjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system that synchronizes a property pane and aproperty view in accordance with the subject invention.

FIG. 2 illustrates a flow chart of a methodology in accordance with aproperty pane of the invention.

FIG. 3 illustrates a flow chart of a methodology in accordance with aproperty browser of the invention.

FIG. 4 illustrates a flow chart of a methodology of populating aproperty pane in accordance with the invention.

FIG. 5 illustrates a screenshot of a minimized property pane inaccordance with the invention.

FIG. 6 illustrates a screenshot of an integrated property pane andvisual component in accordance with the invention.

FIG. 7 illustrates a screenshot of an interaction that is synchronizedbetween the property pane and browser component, in accordance with theinvention.

FIG. 8 illustrates a screenshot of an interaction in the view componentthat is reflected back to the property component, in accordance with theinvention.

FIG. 9 illustrates a screenshot of an interaction that limits a queryscope, in accordance with the invention.

FIG. 10 illustrates a system that employs machine learning in accordancewith the invention.

FIG. 11 illustrates a block diagram of a computer operable to executethe disclosed architecture.

FIG. 12 illustrates a schematic block diagram of an exemplary computingenvironment in accordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION

The invention is now described with reference to the drawings, whereinlike reference numerals are used to refer to like elements throughout.In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the invention. It may be evident, however, that theinvention can be practiced without these specific details. In otherinstances, well-known structures and devices are shown in block diagramform in order to facilitate describing the invention.

As used in this application, the terms “component” and “system” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution. For example, a component can be, but is not limited to being,a process running on a processor, a processor, an object, an executable,a thread of execution, a program, and/or a computer. By way ofillustration, both an application running on a server and the server canbe a component. One or more components can reside within a processand/or thread of execution, and a component can be localized on onecomputer and/or distributed between two or more computers.

As used herein, the term to “infer” or “inference” refer generally tothe process of reasoning about or inferring states of the system,environment, and/or user from a set of observations as captured viaevents and/or data. Inference can be employed to identify a specificcontext or action, or can generate a probability distribution overstates, for example. The inference can be probabilistic—that is, thecomputation of a probability distribution over states of interest basedon a consideration of data and events. Inference can also refer totechniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether or not the events are correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources.

Referring now to FIG. 1, there is depicted a system 100 thatsynchronizes a property pane and a property view in accordance with thesubject invention. The invention is an improved user interface (UI)object for use in metadata management. Document metadata includes one ormore properties (e.g., author, title, subject, data created, category,keywords, to name just a few) that can be exposed for management, e.g.,editing and control. The UI object includes a property editing controlin which the property editing fields and the view of a property-basedbrowser are synchronized, providing both feedback on property changesand a capability to manipulate properties graphically. Direct visualfeedback is provided to the user between the browser and the propertyfields in a property pane so that as the user selects a property in theproperty pane (when the browser is open), the browser automaticallyswitches to grouping by that property. This feedback capability hasanalogies to an existing SaveAs dialog control, which is a userinterface control used for determining where and under what name tostore a file. This enhances the learning curve for users.

In support thereof, a property component 102 is provided thatfacilitates the presentation to a user of a property pane that furtherpresents property information in the form of text that is associatedwith a file. The system 100 also includes a viewing component 104 thatinterfaces to the property component 102 and facilitates viewing agraphical representation of the property information and/or further dataassociated with the properties. One example of a viewing mechanism is abrowser. The viewing component 104 provides for the presentation of atleast the following: a list of common properties (labels) that may beset; a list of existing/allowed property values for each property, wherethe property can be set to the value with a simple click; showing thelist of other files that have a given property value to help making achoice about grouping together; and, copying of properties (labels) froman existing file to the saved one (setting properties by example).

A synchronization component 106 interfaces to both the propertycomponent 102 and the viewing component 104 to facilitate thesynchronization or instantaneous update of changes between the propertycomponent 102 and the viewing component 104. Thus, when the user hasboth the property pane and the browser window open, making a change tothe property pane will be automatically reflected substantiallyimmediately to the browser window, and making a change in the browserwindow will be reflected substantially instantaneously in the propertypane.

FIG. 2 illustrates a methodology in accordance with a property pane ofthe invention. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein, e.g., in the form of a flow chart,are shown and described as a series of acts, it is to be understood andappreciated that the invention is not limited by the order of acts, assome acts may, in accordance with the invention, occur in a differentorder and/or concurrently with other acts from that shown and describedherein. For example, those skilled in the art will understand andappreciate that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the invention.

At 200, a user selects a property item in the property pane. At 202, ifthe browser is open, the browser switches to grouping by the selectedproperty. Note that the grouping can be by stacking or by a propertytree, for example. At 204, the user enters or selects a property valuefor the property in a property pane. At 206, this interaction isinstantaneously reflected visually in the browser.

For example, clicking on an author field can result in showing the filesstacked by author, with the default author (the current user name)selected (or highlighted). When the user types in an additional name,the corresponding stack also gets highlighted. If this is a new name, anew stack is generated and added (with a document “ghost” inside). Theconcept of a document ghost is described in detail hereinbelow.

Note also that the system can be made configurable according to a userprofile or preferences setting to automatically open the browser whenthe user interacts with the property pane. This can be an alternative tothe user manually selecting an “Open Browser” radio button or menuselection, for example.

FIG. 3 illustrates a methodology in accordance with controlling aproperty browser of the invention. At 300, the user chooses a propertyto group by in the browser. At 302, the system determines if theproperty is user settable. If so, at 304, the system next determines ifthe property field is visible in the property pane. This is anindication that the property may need to be added to the property pane(and not that it is out of view, but viewable by scrolling a scrollbar).If the property field was not visible (e.g., the user selected a customproperty called “Project”) it will be automatically added to the pane,as indicated at 306. At 308, the system makes the added propertyvisible. Where the pane is sufficiently large, the added field will bevisible. Otherwise, the property pane can be made scrollable with ascrollbar such that if needed, the user can scroll to view the addeditem. At 310, the visible property is then highlighted. At 302, if theproperty is not user settable, any attempted user interaction isignored, as indicated at 312, and flow is back to 300. Similarly, at306, if the property field is visible, flow is to 310 where the field ishighlighted.

Referring now to FIG. 4, there is depicted a methodology of populating aproperty pane in accordance with the invention. At 400, the user logsinto the system. This can be a login process associated with a clientlogin and/or a network login, for example. At 402, the systemautomatically populates the property pane with the default propertysettings and format. At 404, the system accesses user information. Thiscan be preferences information that the user configures and/or otherinformation stored and enabled in response to the system accessing userlogin information (client and/or network). At 406, the system populatesthe property pane with custom settings that are configured by the user.The custom settings can include all of the default settings plus somenon-default settings, overlap with the default settings to include someof the default settings and some of the non-default settings, or benon-overlapping to include only non-default settings and not include anyof the default settings. At 408, the system operates to synchronizechanges or interactions between the property pane and the browser.

Note that in another implementation, the user can be provided a limitedcapability to change the format or cosmetics of the property pane and/orproperty browser. For example, the user can change aspects such ascolor, font, text size, property pane window size, to name just a few.

In yet another implementation, the custom settings automatically“bubble” to the top of the property pane, since these are likely to bethe preferred properties for immediate viewing by the user (withouthaving to scroll, for example). When the user selects a group in thebrowser, the custom property field substantially instantaneously changesto reflect the selection.

Browsing through immutable properties that are not normallyuser-settable (like Date or Size) would have no effect, except forallowing to narrow down the visible scope. The same applies to browsingthough immutable dynamic lists. The system provided the user withimmediate visible feedback that no property was set in the course ofnavigation, since no property was selected in the property pane. Forexample, the user may have many “Projects” on the user machine, and canchoose to narrow down the browser scope to items modified in the lastmonth to quickly limit the list of “Projects” to those that are stillactive.

In a concept called query refinement, the user can choose to query filesaccording to more than one property. Thus, the user can combine Author,Date, and Document Type to more quickly narrow a search for relatedfiles.

Referring now to FIG. 5, there is illustrated a screenshot 500 of aminimized property pane in accordance with the invention. Whenconsidering a query-oriented file system, the meaning and functionalityof Save and metadata editing commands can change. On such systems, afile browser can retrieve the files based on file properties. Therefore,traditional folder system will not be the only classification method.Moreover, the system will allow for multiple files with the same nameand other user-assigned properties. The files can be distinguished by aglobal unique internal identifier (GUID) and immutable properties (e.g.,creation/last modification date/time). It the light of these changes oradded capabilities, two updated Save-related commands are provided.

Save. If a new document has never been saved before, Save will invokeSaveAs. Otherwise, Save can be used to save a version of the file. Notethat many contemporary applications have no need to save the documentexplicitly, as the programs may have the capability to remember all thechanges automatically. Together with the potential to store multipleversions of the same document, the real meaning of user-initiated Saveis to create a checkpoint, i.e., a separate version that can beretrieved later (thus replacing a Versions command).

SaveAs. The main purpose of SaveAs is to assign properties needed forthe file retrieval. In a database-oriented system, the file can beretrieved by any set of file properties, not just file path.Consequently, the SaveAs dialog can used to set all these properties.There is no need for a separate Properties dialog, since itsfunctionality is taken over by SaveAs.

In the minimized SaveAs property pane 500, the SaveAs command can be aplace to assign all user-settable document properties. It can proposethe default and best-guess values for these properties, so the user needonly click Save (or “OK” where such a button is provided) to accept thechoices and initiate saving of the file.

The minimized SaveAs property pane dialog 500 is particularly appealingto users who are satisfied with the default values of metadataproperties. It is hardly enough, however, if the document requires amore advanced classification mechanism. Many prospective users willstill prefer the folder look. In support thereof, an “Open Browser”button is provided that appends a visual element to the property pane byplacing the file in a specific place, which reintroduces the preferredsynergy between SaveAs, Open, and Windows Explorer. Otherwise, a user isnot provided a means to retrieve a file, and he/she is not alwaysconfident they will be able to do it indirectly via more complex steps.

The following discloses how visual components can be integrated into aproperty editing control. They are described in a context of a SaveAsdialog, but have a broader range of applications—all metadata editingcontrols can use the same ideas. In particular, a file browser canprovide a command to edit properties of an existing file; the dialog toedit these properties can have a very similar design, even if thefunctionality does not involve saving the file to the disk.

Referring now to FIG. 6, a screenshot 600 shows an integrated propertypane and visual component in accordance with the invention. A differentview from the minimal SaveAs design is to add a browsing component. Thedifferent view can be provided as being more useful in some cases foruser viewing, but too complicated in others. The browser implementationallows viewing files clustered by various properties. In a WINDOWS XPbrand operating system environment, for example, navigating to aspecific folder meant putting the saved file there. In thequery-oriented browser, navigating to a specific property cluster meansassigning that property value to the file being saved. The functionalitybuilds on the experience with which users are familiar.

There are, however, significant differences from a WINDOWS XP brandoperating system environment. Previously, there was just one folder treeto navigate. When dealing with a properties-based file system, there canbe many properties to which a value can be assigned. The navigationalspace becomes multi-dimensional, with multiple property axes toconsider. Additionally, there can be storage favorites (e.g.,collections of multiple predefined property values) that cut acrosssingle-property trees. Since users typically visualize only onedimension at a time (without significant confusion), visual confirmationof the choices is provided when switching between different clusterdimensions.

One solution involves use of a “Save Ghost” feature, which is a visualrepresentation of the file being saved. Ghost is a projection or previewof what is about to be saved. The use of Save Ghost has a number ofadvantages. It provides a simple way to visualize where the file goesand what will be its peers, and enhances the meaning of the propertyclusters as a location to save to and retrieve from. Save Ghost providesa handle for direct manipulations. For example, dragging the save ghostfrom “a Word brand Document” to “Text Documents” can have a meaning ofchanging the document type from Word to Text. In ordered lists, the saveghost can be dragged into the proper position.

Save Ghost provides feedback for invalid property values and immutableproperties. For example, navigation to an EXCEL brand spreadsheetdocument cluster may not show the save ghost there because saving Worddocuments in Excel format is not supported. Similarly, a view ofdocuments from a previous week does not include the new document becauseit will be always saved with the current date. At the same time, the useof save ghost enables exploratory navigation to places where the filecannot be saved. Without it, navigation to EXCEL brand spreadsheetdocuments or documents from a previous week would have to be disallowed(to imply that these are invalid locations.)

The screenshot of FIG. 6 provides a migration path for the currentWINDOWS XP brand operating system users. Since the folder location isexposed as one of the file properties, users can initially stick to theknown folder navigation rules, and the dialog will provide all thefunctionality and capabilities of the current SaveAs dialog. Thisincludes one-click copying of all the properties to replace an existingfile. As the user becomes more confident with the new interface, theywill start using more and more of the few features. However, onedrawback of this design is the lack of clear feedback as to how thebrowser component can be used to set the file properties. There is novisible connection (or interaction) between the top part (propertysettings) and the bottom part (browsing). Even if the properties dialogprovides all the desired capabilities, its usage may be confusing.

Referring now to FIG. 7, a screenshot 700 shows an interaction that issynchronized between the property pane and browser component, inaccordance with the invention. Whenever possible, the browser viewcorresponds to the property being edited, and vice versa. When userselects a property to edit (with the exception of free-form propertieslike file name or comments,) the browser view switches automatically tothe view clustered by that very property. Moreover, the cluster in viewcorresponds to the currently assigned property value (when available).

When a user selects or types in a new value for the property in theproperty pane, the view in the browser window changes as soon as the newvalue is confirmed (e.g., by pressing Enter). This behavior has someanalogy in the current SaveAs dialog, where the folder view can beswitched by typing in folder path in the file name edit box. Formulti-valued properties (e.g., Author or Keywords) the browser viewshows an intersection of individual property values (e.g., documentsauthored by all authors on the list.)

Referring now to FIG. 8, there is illustrated a screenshot 800 of aninteraction in the view component that is reflected back to the propertycomponent, in accordance with the invention. When a user starts browsingthe property tree in the browser window, displaying the clustered viewbased on any mutable property automatically visually activates thecorresponding property editing field in the property pane. This providesa direct feedback as to which property is being set and to what value itis set. Switching between different property clusters automatically setsthe property to the corresponding property value. Multi-value propertiescan be set by selecting multiple property clusters in the viewer, orthrough checkboxes next to the cluster name. When the view in thebrowser is pivoted on an immutable property (e.g., Date) none of theproperty editing fields is visually activated, and switching betweendifferent clusters does not set any property.

A special type of browser view shows the contents of storage favorites802, which can be defined as groups of items sharing same values for oneor more properties. When a view is switched to a storage favorite (whichimplies putting the new file into that group), a number of fileproperties can be visually activated showing all the properties affectedby the switch and the browser view can be switched to show the otherfiles belonging to this storage favorite location (i.e., sharing thesame property values).

The disclosed synchronization mechanism between the property editingfields and property-based browser has multiple advantages. It showsvisually that property values can be used to classify files on the disk.This in turn encourages a user to provide meaningful metadata.Synchronization aids in educating users that the same browsing methodscan be used later to find and retrieve the file. It combines the best ofboth worlds when assigning the property value: property editing fieldsare particularly useful for entering new values (e.g., new keywords)while the browser provides an enumeration of existing values togetherwith feedback as how they are used. Synchronization is intuitive byfocusing the dialog functionality on its main purpose, which is to setthe file properties. Additionally, it minimizes the cases when thebrowser view is totally unrelated to the file being saved.

FIG. 9 illustrates a screenshot 900 of an interaction that limits aquery scope, in accordance with the invention. Here, the scope islimited to a certain type of document—WORD brand word processingdocuments, by locking property values. One of the most useful featuresof the property-based browser is an ability to browse within the resultset of the previous query. For example, a query can be made for all thefiles of type Word Document and then view the results clustered by theAuthor property. The user interface can provide ways to “pin” theresults of a query, whether it is by a double-click command, a commandon a right-click menu, or a pin button next to the query cluster. Oncethe query is pinned, all subsequent browsing is done within the resultset of the query.

The browsing component of the SaveAs dialog has the same pinningcapability as the standalone browser. For example, a user can pin thescope to Type: Word Document. This has analogy to the functionality ofthe standard SaveAs dialog, where setting the file type limits thebrowser view to files with the same extension. The new SaveAs dialoggoes further by allowing pinning about any file property: e.g., folder,keyword, author, and so on.

However, limiting the browser scope in the conventional SaveAs dialogwas automatic. As soon as the file type was selected, the view waslimited to files of that type. Such an approach is too confusing whennow dealing with multiple metadata properties. Thus, in the new SaveAsdialog of the subject invention, it is applied only to the storagefavorites: selecting one of the favorite places (see the icons in theright top row of FIG. 9) sets the global scope of the browser. Theglobal scope is set to All Items by default (or whatever the userselection is for the default scope), and remains the same untilexplicitly changed or limited by a subsequent pinning operation.

Since the disclosed architecture ties SaveAs browsing to propertyediting, the effects of “pinning” on property editing is considered.Pinning limits the browser scope to items with certain properties.Logically, it is assumed that the file being saved acquires the sameproperties (whenever possible). Moreover, since pinning prevents goingoutside of the property scope, the properties should be consideredlocked into a read-only status. Therefore, pinning the query in thebrowser and locking the property value are two equivalent operations.

Locking property values is a new concept, and is particularly usefulwith storage favorites. Assume that a user creates a place (storagefavorite) that contains “My Word documents about SaveAs” (i.e., Worddocuments with SaveAs keyword where the user is one of the authors). Ifthe user chooses to put a new document into that group, it shouldacquire certain values for Type, Keyword, and Author properties. Now, ifthe user pins that storage favorite, the property values get locked. Theuser can still modify other properties, or even add additional values tothe locked ones (e.g., additional keywords or authors), but the lockprevents the user from accidentally removing or modifying the propertyvalues that are critical for the desired group membership. This is anadvanced concept (e.g., similar to read-only files), but advanced userswill appreciate it.

It is also possible to pin the query without locking the propertyvalues. This can happen for queries pivoted on immutable properties. Forexample, a user can pin a query that looks for files from the lastthirty days. This limits the browser scope to the last thirty days, butit will not affect the properties of the file being saved.

Referring now to FIG. 10, there is illustrated a system 1000 thatemploys machine learning in accordance with the invention. The subjectinvention (e.g., in connection with property presentation) can employvarious artificial intelligence based schemes for carrying out variousaspects of the subject invention. For example, a process for determiningwhat properties to present for a given user can be facilitated via anautomatic classifier system and process 1002. The classifier 1002interfaces to the property component 102, viewing component 104, andsynchronization component 106 to facilitate automation of certainfeatures of the system 1000 based on inferences made according to userinteractions and user data, for example.

A classifier is a function that maps an input attribute vector, x=(x1,x2, x3, x4, xn), to a confidence that the input belongs to a class, thatis, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed.

A support vector machine (SVM) is an example of a classifier that can beemployed. The SVM operates by finding a hypersurface in the space ofpossible inputs, which hypersurface attempts to split the triggeringcriteria from the non-triggering events. Intuitively, this makes theclassification correct for testing data that is near, but not identicalto training data. Other directed and undirected model classificationapproaches include, e.g., naïve Bayes, Bayesian networks, decisiontrees, and probabilistic classification models providing differentpatterns of independence can be employed. Classification as used hereinalso is inclusive of statistical regression that is utilized to developmodels of priority.

As will be readily appreciated from the subject specification, thesubject invention can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing user behavior, receiving extrinsic information). Forexample, SVM's are configured via a learning or training phase within aclassifier constructor and feature selection module. Thus, theclassifier(s) can be used to automatically perform a number offunctions, including but not limited to maintaining relationshipsbetween an e-mail and its attachment. In another implementation, therelationship is processed more extensively, for example, the e-mail isrelated to a meeting that is further related to a group of people whoattended the meeting (or who were scheduled to attend, but did not), andwho are related to this client. Thus, the relationships can bemaintained as a string to find the desired file.

The classifier can also be employed to bubble-up the relationships tothe properties pane for a given user, as these can be preferred for bythe user according to user preferences. Moreover, while saving therelated files, the system can automatically connect to thoserelationships.

In yet another implementation, the classifier learns from userinteraction and reacts accordingly to automate the properties displayedin the properties pane according to use interaction history. A userprofile can trigger a custom set of properties. The custom set can bemodified over time based on use, manual modification, and userinteraction with the properties and/or browser window. The propertieswill then be displayed accordingly.

In still another implementation, the classifier facilitates notifyingusers of a thread in response to an update made to a file associatedwith that thread. The associated users are then notified automatically,and perhaps when the file is saved.

The displayed properties can also be selected based on the type of data.For example, if the user routinely deals with two types of data such asfinancial data and human resources data, depending on what the userchooses to interact, the properties will be adjusted accordingly.Another example includes music data where the artist property isautomatically presented as a property in the property pane. If the datais related to pictures, the properties displayed can include locationand people. For documents, the property can also include case filenumber, etc. Any or all of these can be made user modifiable.

Referring now to FIG. 11, there is illustrated a block diagram of acomputer operable to execute the disclosed architecture. In order toprovide additional context for various aspects of the invention, FIG. 11and the following discussion are intended to provide a brief, generaldescription of a suitable computing environment 1100 in which thevarious aspects of the invention can be implemented. While the inventionhas been described above in the general context of computer-executableinstructions that may run on one or more computers, those skilled in theart will recognize that the invention also can be implemented incombination with other program modules and/or as a combination ofhardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the invention may also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media can comprise computer storage mediaand communication media. Computer storage media includes both volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules or other data.Computer storage media includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digital videodisk (DVD) or other optical disk storage, magnetic cassettes, magnetictape, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store the desired information andwhich can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 11, there is illustrated an exemplaryenvironment 1100 for implementing various aspects of the invention thatincludes a computer 1102, the computer 1102 including a processing unit1104, a system memory 1106 and a system bus 1108. The system bus 1108couples system components including, but not limited to, the systemmemory 1106 to the processing unit 1104. The processing unit 1104 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures may also be employed as theprocessing unit 1104.

The system bus 1108 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1106includes read only memory (ROM) 1110 and random access memory (RAM)1112. A basic input/output system (BIOS) is stored in a non-volatilememory 1110 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1102, such as during start-up. The RAM 1112 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1102 further includes an internal hard disk drive (HDD)1114 (e.g., EIDE, SATA), which internal hard disk drive 1114 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1116, (e.g., to read from or write to aremovable diskette 1118) and an optical disk drive 1120, (e.g., readinga CD-ROM disk 1122 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1114, magnetic diskdrive 1116 and optical disk drive 1120 can be connected to the systembus 1108 by a hard disk drive interface 1124, a magnetic disk driveinterface 1126 and an optical drive interface 1128, respectively. Theinterface 1124 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1102, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the exemplary operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the invention.

A number of program modules can be stored in the drives and RAM 1112,including an operating system 1130, one or more application programs1132, other program modules 1134 and program data 1136. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1112. It is to be appreciated that the invention canbe implemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1102 throughone or more wired/wireless input devices, e.g., a keyboard 1138 and apointing device, such as a mouse 1140. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1104 through an input deviceinterface 1142 that is coupled to the system bus 1108, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1144 or other type of display device is also connected to thesystem bus 1108 via an interface, such as a video adapter 1146. Inaddition to the monitor 1144, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1102 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1148. The remotecomputer(s) 1148 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1102, although, for purposes of brevity, only a memory storage device1150 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1152 and/orlarger networks, e.g., a wide area network (WAN) 1154. Such LAN and WANnetworking environments are commonplace in offices, and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich may connect to a global communication network, e.g., the Internet.

When used in a LAN networking environment, the computer 1102 isconnected to the local network 1152 through a wired and/or wirelesscommunication network interface or adapter 1156. The adaptor 1156 mayfacilitate wired or wireless communication to the LAN 1152, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adaptor 1156.

When used in a WAN networking environment, the computer 1102 can includea modem 1158, or is connected to a communications server on the WAN, orhas other means for establishing communications over the WAN 1154, suchas by way of the Internet. The modem 1158, which can be internal orexternal and a wired or wireless device, is connected to the system bus1108 via the serial port interface 1142. In a networked environment,program modules depicted relative to the computer 1102, or portionsthereof, can be stored in the remote memory/storage device 1150. It willbe appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computerscan be used.

The computer 1102 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with conventional network or simply an ad hoc communicationbetween at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room or a conference room at work,without wires. Wi-Fi is a wireless technology like that used by acellular telephone that enables such devices, e.g., computers, to sendand receive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, withan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate or with productsthat contain both bands (dual band), so the networks can providereal-world performance similar to the basic 10BaseT wired Ethernetnetworks used in many offices.

Referring now to FIG. 12, there is illustrated a schematic block diagramof an exemplary computing environment 1200 in accordance with theinvention. The system 1200 includes one or more client(s) 1202. Theclient(s) 1202 can be hardware and/or software (e.g., threads,processes, computing devices). The client(s) 1202 can house cookie(s)and/or associated contextual information by employing the invention, forexample. The system 1200 also includes one or more server(s) 1204.

The server(s) 1204 can also be hardware and/or software (e.g., threads,processes, computing devices). The servers 1204 can house threads toperform transformations by employing the invention, for example. Onepossible communication between a client 1202 and a server 1204 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The data packet may include a cookie and/orassociated contextual information, for example. The system 1200 includesa communication framework 1206 (e.g., a global communication networksuch as the Internet) that can be employed to facilitate communicationsbetween the client(s) 1202 and the server(s) 1204.

Communications can be facilitated via a wired (including optical fiber)and/or wireless technology. The client(s) 1202 are operatively connectedto one or more client data store(s) 1208 that can be employed to storeinformation local to the client(s) 1202 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1204 areoperatively connected to one or more server data store(s) 1210 that canbe employed to store information local to the servers 1204.

What has been described above includes examples of the invention. It is,of course, not possible to describe every conceivable combination ofcomponents or methodologies for purposes of describing the invention,but one of ordinary skill in the art may recognize that many furthercombinations and permutations of the invention are possible.Accordingly, the invention is intended to embrace all such alterations,modifications and variations that fall within the spirit and scope ofthe appended claims. Furthermore, to the extent that the term “includes”is used in either the detailed description or the claims, such term isintended to be inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system having computer executable instructionsembodied on one or more memory storage devices that when executed on oneor more processors facilitates metadata management, comprising: apreview representation of a file that is selected to save; a propertycomponent that generates a first cluster of peer files in response toreceiving a first user input selecting the file that is selected to saveand receiving a second user input associating a first common value for aproperty with the file that is selected to save, wherein each file inthe first cluster shares the first common value for the property, andwherein prior to saving the file, the first cluster includes the previewrepresentation of the file that is selected to save; and asynchronization component that synchronizes communication between theproperty component and a viewing component to facilitate substantiallyimmediate updating of changes between the property component and theviewing component, wherein the viewing component displays the firstcluster of files upon the user selecting the file that is selected tosave and associates the first common value with the file that isselected to save.
 2. The system of claim 1, wherein the first cluster offiles is displayed as a stack of files.
 3. The system of claim 1,wherein the preview representation of the file in the first clusterprovides an indication that the first common value that is shared byeach file in the first cluster is invalid for the file that is selectedto save.
 4. The system of claim 3, wherein the first common value is adocument format.
 5. The system of claim 1, wherein upon the userselecting the file that is selected to save and associating a secondcommon value with the file that is selected to save, the propertycomponent generates a second cluster of files where each file in thesecond cluster has the second common value for a property, the secondcluster including the preview representation of the file that isselected to save.
 6. The system of claim 4, wherein the synchronizationcomponent synchronizes communication between the property component andthe viewing component, wherein the viewing component displays the secondcluster of files upon the user selecting the file that is selected tosave and associating the second common value with the file that isselected to save.
 7. The system of claim 5, wherein the second clusteris displayed as a new stack of files.
 8. The system of claim 5, whereinthe preview representation of the file in the second cluster provides anindication that the second common value that is shared by each file inthe second cluster is invalid for the file that is selected to save. 9.The system of claim 1, wherein upon the user selecting the file that isselected to save and associating a plurality of common values with thefile that is selected to save, the property component generates acluster of files for each of the plurality of common values, where eachfile in a cluster has a common value for a property, each clusterincluding the preview representation of the file that is selected tosave.
 10. The system of claim 9, wherein the synchronization componentsynchronizes communication between the property component and theviewing component, wherein the viewing component displays each clusterof files upon the user selecting the file that is selected to save andassociating each of the plurality of common values with the file that isselected to save.
 11. A method for facilitating metadata management,comprising: receiving, in a property pane, an input selecting a file tosave; providing, in an output interface of a computer, a previewrepresentation of the file that is selected to save; receiving, in theproperty pane, an input associating a plurality of common values for acorresponding plurality of properties with the file that is selected tosave; responsive to receiving the input selecting the file that isselected to save and the input associating the plurality of commonvalues for the corresponding plurality of properties with the file thatis selected to save: A) generating a corresponding cluster of files foreach of the plurality of common values for the plurality of properties,where a) each file in at least a first cluster has a common value for afirst property of the plurality of properties, b) each file in a secondcluster has a common value for a second property of the plurality ofproperties, and c) each cluster includes the preview representation ofthe file that is selected to save; B) synchronizing communicationbetween the property pane and a viewing pane to facilitate substantiallyimmediate updating of changes between the property pane and the viewingpane; and C) displaying the first cluster of files in the viewing pane.12. The method of claim 11, a first cluster of files displaying as astack of files.
 13. The method of claim 11, the preview representationof the file in the first cluster providing an indication that the firstcommon value that is shared by each file in the first cluster is invalidfor the file that is selected to save.
 14. The method of claim 13,wherein the first common value is a document format.
 15. The method ofclaim 11, displaying each cluster of files in the viewing pane upon theuser selecting the file that is selected to save and associating each ofthe plurality of common values with the file that is selected to save.16. One or more memory storage devices having computer executableinstructions embodied thereon that when executed on one or moreprocessors facilitates a method of metadata management, the methodcomprising: providing a preview representation of a file that isselected to save; upon receiving a first user input selecting the filethat is selected to save in a property pane and receiving a second userinput associating a first common value for a property with the file thatis selected to save, generating a first cluster of files where each filein the first cluster shares the first common value for the property, andwherein prior to saving the file, the first cluster includes the previewrepresentation of the file that is selected to save; synchronizingcommunication between the property pane and a viewing pane to facilitatesubstantially immediate updating of changes between the property paneand the viewing pane; and displaying the first cluster of files in theviewing pane upon the user selecting the file that is selected to saveand associating the first common value with the file that is selected tosave, the preview representation of the file in the first clusterproviding an indication that the first common value that is shared byeach file in the first cluster is invalid for the file that is selectedto save.
 17. The one or more memory storage devices of claim 16, themethod further comprising upon the user selecting the file that isselected to save and associating a plurality of common values with thefile that is selected to save, generating a cluster of files for each ofthe plurality of common values, where each file in a cluster has acommon value for a property, each cluster including the previewrepresentation of the file that is selected to save.
 18. The one or morememory storage devices of claim 17, the method further comprisingdisplaying each cluster of files in the viewing pane upon the userselecting the file that is selected to save and associating each of theplurality of common values with the file that is selected to save. 19.The system of claim 5, wherein the first and second clusters of filesinclude subspaces of a navigational space with a variable number ofdimensions greater than one, the variable number of dimensionscontaining substantially all existing files of the system, wherein anaxis of the dimension of the navigational space corresponding to thevariable number of dimensions represents an nth property that may beassociated with substantially any existing file of the system.
 20. Thesystem of claim 1, wherein a Save Ghost feature provides the previewrepresentation.